Coordinated Access to a Satellite Link Using Data Profiles

ABSTRACT

Apparatuses, methods, and systems for coordinated access to a wireless link through data profiles are disclosed. One method includes receiving through the wireless link, by each hub associated with a base station, one or more data profiles from a network management element, receiving, by each hub, data from data sources associated with the hub, controlling, by each hub, a timing of communication of the data for each of the data sources from the hub to the base station through the wireless satellite link based on the one or more data profiles, monitoring reporting times of different data sources of different hubs over time, allocating preamble codes to each of the data sources, wherein different preamble codes are allocated to different data sources of different hubs that report within a margin of time of each other, and inserting the allocated preamble codes into packets of each of the data sources.

RELATED PATENT APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 16/396,651, filed Apr. 27, 2019, which is herein incorporatedby reference.

FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to satellite communications.More particularly, the described embodiments relate to systems, methodsand apparatuses for coordinated access to a satellite link using dataprofiles.

BACKGROUND

Current data networks are designed primarily for human users and thenetwork and traffic characteristics that human users generate. Thegrowth and proliferation of low-cost embedded wireless sensors anddevices pose a new challenge of high volumes of low bandwidth devicesvying for access to limited network resources. One of the primarychallenges with these new traffic characteristics is the efficiency atwhich the shared network resources can be used. For common low bandwidthapplications such a GPS tracking, the efficiency (useful/useless dataratio) can often be below 10%. This inefficiency is the result of largevolumes of devices communicating in an uncoordinated environment.Addressing this problem is fundamental to the future commercialviability of large-scale sensor network deployments.

It is desirable to have methods, apparatuses, and systems forcoordinated access to a satellite link using data profiles.

SUMMARY

An embodiment includes a method of coordinating access of a plurality ofdevices across a wireless link. The method includes receiving through awireless link, by each hub of a plurality of hubs associated with a basestation, one or more data profiles from a network management element,receiving, by each hub, data from the one or more data sourcesassociated with the hub, controlling, by each hub, a timing ofcommunication of the data for each of the one or more data sources fromthe hub to the base station through the wireless satellite link based onthe one or more data profiles, monitoring reporting times of differentdata sources of different hubs over time, allocating preamble codes toeach of the data sources, wherein different preamble codes are allocatedto different data sources of different hubs that report within a marginof time of each other, and inserting the allocated preamble codes intopackets of each of the data sources, wherein the one or more dataprofiles of each of the hubs maintain synchronous timing of thecommunication of the data of each of the hubs with respect to eachother.

Another embodiment includes a system for coordinating access of aplurality of devices across a satellite link. The system includes atleast one base station, the at least one base station operative tocommunicate with each of a plurality of hubs through a wirelesssatellite link, wherein each of the hubs are connected to one or moredata sources. Each hub is operative to receive through the wireless linkone or more data profiles back from a network management element,receive data from the one or more data sources associated with the hub,control a timing of communication of the data for each of the one ormore data sources from the hub to the base station through the wirelesssatellite link based on the data profile, wherein reporting times ofdifferent data sources of different hubs are monitored over time,wherein preamble codes are allocated to each of the data sources,wherein different preamble codes are allocated to different data sourcesthat report within a margin of time of each other, wherein each hubfurther operates to insert the allocated preamble codes into packets ofeach of the data sources, and wherein the data profile of each of thehubs maintain synchronous timing of the communication of the data ofeach of the hubs with respect to each other.

Other aspects and advantages of the described embodiments will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, illustrating by way of example theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a plurality of hubs that communicate data of data sourcesthrough a satellite link to a base station, according to an embodiment.

FIG. 2 shows packet interference due to variations in propagation timebetween the base station and multiple different hubs, according to anembodiment.

FIG. 3 shows multiple sources for providing updates or feedback of dataprofiles, according to an embodiment.

FIG. 4 shows data profiles, according to an embodiment.

FIG. 5 shows results of data smoothing due to data source profileadjustment, according to an embodiment.

FIG. 6 shows control channel efficiencies and the effects assignments ofpreamble codes can have on the control channel efficiencies, accordingto an embodiment.

FIG. 7 a dynamic allocation of control channel versus data channel,according to an embodiment.

FIG. 8 is a flow chart that includes steps of a method of coordinatingaccess of a plurality of devices across a satellite link, according toan embodiment.

FIG. 9 shows a plurality of hubs that communicate data of data sourcesthrough a shared resource to a base station, according to an embodiment.

DETAILED DESCRIPTION

The embodiments described include methods, apparatuses, and systems forcoordinated access to a satellite link using data profiles. For at leastsome embodiments, the data profile allows a range of network accesstechniques to be simultaneously supported on a hub. This allows, forexample, a hub that includes a data device such as a temperature sensorand another data device such as a mobile point of sale terminal toemploy multiple data reporting techniques. For at least someembodiments, the data profiles allow routing and management of the dataon a per packet level rather than on a data device level. That is, forexample, the data profile of a data device may dictate that differentpackets of the data device may be communicated or reported differently.For example, temperature data (packets) may be reported periodically,but if the temperature exceeds a specified level, the temperature data(packets) is reported in real-time.

For an embodiment, channel and transmission characteristics are known apriori for deterministic data types which can be used to significantlyreduce the overhead on the network spent on passing this informationbetween a hub and a base station. For at least some embodiments,transmissions by a hub of multiple disparate devices can be coordinatedby a network management element via the data profiles andsynchronization (that is, synchronization between different datadevices) of packets provides traffic spreading and reduces the need forrandom access and other channel contention resources. For at least someembodiments, hub transmission timing can be coordinated betweengeographically disparate devices to eliminate the contention for sharednetwork resources only for applicable application types such as periodicor schedule data while preserving the flexibility of real timetransmissions.

FIG. 1 shows a plurality of hubs 110, 190 that communicate data of datasources 111, 112, 113, 114, 115 through satellite link(s) 116, 117 to abase station 140, according to an embodiment. As shown, the data sources111, 112, 113, 114, 115 are connected to the hubs 110, 190. The hubs110, 190 communicate through modems 130, 132 to a modem 145 of the basestation 140 through the wireless satellite links 116, 117. The basestation may also communicate with outside networks 170, 180. For anembodiment, the wireless satellite links 116, 117 reflectively passthrough a satellite 191.

It is to be understood that the data sources 111, 112, 113, 114, 115 canvary in type, and can each require very different data reportingcharacteristics. The wireless satellite links 116, 117 links are alimited resource, and the use of this limited resource should bejudicious and efficient. In order to efficiently utilize the wirelesssatellite links 116, 117, each of the data sources 111, 112, 113, 114,115 are provided with data profiles (shown as Dev profiles as a profilemay be allocated for each device) 121, 122, 123, 124, 125 thatcoordinate the timing (and/or frequency) of reporting (communication bythe hubs 110, 190 to the base station 140 through the wireless satellitelinks 116, 117) of the data provided by the data sources 111, 112, 113,114, 115.

For an embodiment, a network management element 150 maintains a database160 in which the data profiles 121, 122, 123, 124, 125 can be stored andmaintained. Further, the network management element 150 manages the dataprofiles 121, 122, 123, 124, 125, wherein the management includesensuring that synchronization is maintained during the data reporting bythe hubs 110, 190 of the data of each of the data sources 111, 112, 113,114, 115. That is, the data reported by each hub 110, 190 of the data ofthe data sources 111, 112, 113, 114, 115 maintains synchronization ofthe data reporting of each of the data sources 111, 112, 113, 114, 115relative to each other. Again, the network management element 150ensures this synchronization through management of the data profiles121, 122, 123, 124, 125. The synchronization between the data sources111, 112, 113, 114, 115 distributes the timing of the reporting of thedata of each of the data sources 111, 112, 113, 114, 115 to prevent thereporting of one device from interfering with the reporting of anotherdevice, and provides for efficiency in the data reporting.

For at least some embodiments, the network management element 150resides in a central network location perhaps collocated with multiplebase stations and/or co-located with a network operations center (asshown, for example, in FIG. 3). For an embodiment, the networkmanagement element 150 directly communicates with the base station 140and initiates the transfer of data profiles across the network via thebase station 140 to the hubs 110, 190.

For at least some embodiments, data profiles are distributed when newhubs are brought onto the network, when hubs change ownership, or whenthe hubs are re-provisioned. Other changes to data profile contentsoutside of these situations are more likely addressed by sync packets(for an embodiment, a sync packet is a packet to update the value of aspecific field inside of a data profile, but not necessarily updatingthe structure of the data profile) where only small changes to profilefields are required.

As described, the data profiles 121, 122, 123, 124, 125 control timingof when the hubs 110, 190 communicate the data of the data sources 111,112, 113, 114, 115 through wireless satellite links 116, 117 (sharedresource). Accordingly, the described embodiments coordinate access tothe shared network resource (wireless satellite links 116, 117) toinsure optimal usage of the network resource to avoid collisions betweenpackets, the transmission of redundant information, and to reshapeundesired traffic profiles.

For at least some embodiments, the data profiles allow for theelimination of redundant data channel setup information which is alreadycontained inside the data profile, which then are no longer needed to beshared upon the initiation of every packet sent across the network. Thisinformation may include the transmission size, sub-carrier (frequency)allocation, MCS (modulation and coding scheme) selection, and timinginformation. The result of this is a reduction in data resourcesconsumed by the network to send a packet of data. In the example ofsending a GPS data packet containing x, y, z, and time, the amount ofredundant channel setup information is 8× larger than the actual GPSdata packet of interest, resulting in a very inefficient network forlarge volumes of narrowband traffic. Additionally, in the realm ofsatellite communications, the elimination of unnecessary channel setupmessages reduces the latency between the initiation of sending, forexample, a GPS packet across the network and actually receiving thatpacket by roughly half. For example, a normally 3 second latency can bereduced to as low as 0.25 seconds.

While FIG. 1 shows each hub as including more than one data source, itis to be understood that each hub may include a single data source.Further, the data of a single data source may be treated differentlybased on the profile. That is, different data packets of the single datasource may be reported, or communicated differently based on the profileof the data device. For example, some data of the data source may bereported or communicated periodically, whereas different data of thedata source may be reported or communicated in real time. For anembodiment, characteristics or properties of the data determine orinfluence the timing of the communication of the data from the hub ofthe data source.

Further, while FIG. 1 shows the hubs and the data sources possibly beingseparate physical devices, it is to be understood that the hub and oneor more data sources may actually be a single physical device.

FIG. 2 shows packet interference due to variations in propagation timebetween the base station 240 and multiple different hubs 210, 212,according to an embodiment. As shown, a first hub (Hub 1) 210 has atransit time of wireless communication between the first hub (Hub 1) 210and a satellite 191 of T1 215. Further, as a second hub (Hub 2) 212 hasa transit time of wireless communication between the second hub (Hub 2)212 and the satellite 191 of T2 216. The variations of the transmittimes between different hubs can be large due to the potentially largewireless coverage footprint of the satellite 191.

For at least some embodiments, transmission delay of wirelesscommunication between hubs 210, 212 and the base station 240 includesthe summation of at least two components, a course delay and a finedelay. The course delay consists of the minimum delay seen by all hubscommunicating to a single base station. Each base station therefore hasa single course delay associated with the base station. For anembodiment, the fine delay is the addition of a delay variance across alarge geography served by a base station. Therefore, the fine delay isdefined on a per hub basis.

For an embodiment, the course delay is transmitted to the hubs 210, 212and stored in the data profile from the network management element viathe base station 240. For an embodiment, the fine delay is similarlytransmitted across the network, or it may be independently inferredbased upon hub location.

An interference condition can result due to the potentially varyingpropagation times between the hubs 210, 212 and the base station 240through the wireless satellite links. For example, as additionally shownin FIG. 2, a packet 230 transmitted from the first hub (Hub 1) 210 tothe base station 240 has the first transmit time T1 215 to the satellite191. Further, as additionally shown in FIG. 2, a packet 232 transmittedfrom the second hub (Hub 2) 212 to the base station 240 has the secondtransmit time T2 216 to the satellite 191. Accordingly, a packetinterfering condition 242 can result when a packet 234 received at thebase station 240 from the first hub (Hub 1) 210 is received at the sametime that a packet 236 received at the base station 240 from the secondhub (Hub 2) 212 is received.

To mitigate the packet interference condition shown in FIG. 2, for atleast some embodiments, the profile for each device is adjusted based atleast in part on a location of the device, wherein the profileadjustment mitigates differences in propagation time of communicationpropagating from each hub to the base station. That is, for example, aGPS (global positioning sensor) device of the hub provides the locationof the hub. The hub can then adjust the profiles of the data sourcesassociated with the hub based on the location of the hub to reduce thepossibility of packet interference due to data reporting by other hubsof data from other date devices.

While this functionality is described using location data, otherembodiments to determine the fine propagation delay include timing ofpreamble positions inside a random access window, signal strengthdetection, or general timing of sync signals

The data profiles of the data source may initially be selected tosynchronize the data reporting. However, due to the differences inpropagation through wireless links to the base station, the describedinterference condition can occur. As described, for an embodiment, thehub reporting the data of the data sources can adjust the profiles toaccount for the differences in propagation delay. For an embodiment, thedifferences in the propagation delay can be accounted for by the GPSlocations of multiple hubs. The data profiles can then be adjusted toaccount for the differences in wireless transmission propagation delaybetween reporting hubs. For an embodiment, the propagation time isdetermined by a time-of-flight of communication between the hub 210 andthe base station 240. The differences in the propagation delays can thenbe accounted for in the data profiles to mitigate interferences betweenreporting hubs.

FIG. 3 shows multiple sources for providing updates or feedback of dataprofiles, according to an embodiment. As described, for an embodiment,the network management element manages the data profiles 121, 122, 123,124, 125 of the data devices 111, 112, 113, 114, 115. At least someembodiments include adjusting the data profile. At least one embodimentincludes the data profile adjustment 364 by sourced by a downstreamdevice, such as, one or more of the hubs 110, 190. At least one otherembodiment includes the data profile adjustment 362 by sourced by, forexample, a network operation center 350.

As stated, for at least some embodiments, the data profiles areadaptively updated based on a top down feedback from the networkoperation center 350 or the network management element 150. For anembodiment, this includes rebalancing preamble codes assigned todifferent data devices to smooth RACH (random access channel) profiles,which is triggered, for example, by the detection of excess (greaterthan a threshold amount) collisions between RACH packets. For anembodiment, the rebalancing includes assigning to the offending devicesdisparate orthogonal preamble codes to mitigate the collisions. For anembodiment, this includes adjusting timing offsets (adjusting the timingoffset includes adjusting the relative timing of periodic reporting) tosmooth network traffic congestion and maintain network utilization forperiodic data below X %, by measuring allocated versus free networkresource units. For an embodiment, this includes updating data profileswhen changing an application of a data device, triggered by user/owneroperator intervention, for example, via a web console. For anembodiment, this includes updating the course round trip delay timing,triggered, for example, by a new hub registration on a base station.

As stated, for at least some embodiments, the data profiles areadaptively updated based on a bottom up feedback from the hubs 110, 190or the data sources 111, 112, 113, 114, 115. For an embodiment, thisincludes the previously described fine round-trip timing delay,constantly updated within the data profiles based upon GPS coordinatesof the hubs 110, 190. For an embodiment, this includes the data profileof a data device being updated by a hub through a communication link tothe hub. For example, a user/operator may proactively update a profilethrough the hub by connecting via wireless phone to the hub. This can beuseful, for example, when the hub is located in a remote location thatis not serviced by a cellular network, and therefore, a user/operatorhas no way of connecting to the network operation center 350 or thenetwork management element 150 without the wireless satellite connectionprovided by the hub. The only way for the user/operator to update one ormore of the data profiles is through the bottom up feedback provided bythe hub.

FIG. 4 shows data profiles, according to an embodiment. The dataprofiles provide coordination of the communication of the data of thedata devices over the shared wireless satellite links. The communicationcan include one or more of real time data reporting, scheduled datareporting, and/or periodic data reporting. The data profile for a givendata device provides the hub associated with the data device the abilityto control a timing of communication of the data for each of the one ormore data sources from the hub to a base station through the wirelesssatellite link. The controlled timing provides for synchronization ofthe communication of the data with respect to the communication of dataof other data source of both the same hub, and for one or more differenthubs. For an embodiment, the data profile additionally provides the hubwith a frequency allocation for the communication of the data of thedata source.

An exemplary generic data profile 410 of FIG. 4 includes enablement ofreal time access or real time reporting of the data of the data device,enablement of scheduled access or scheduled reporting of the data of thedata device, and enablement of periodic access or periodic reporting ofthe data of the data device. Further, for an embodiment, the dataprofile also includes an estimated MCS (modulation and coding scheme).Further, for an embodiment, the data profile also includes a dataprocessing function.

A specific example of a data profile 420 provides for reporting of thelocation of a data device. This could be, for example, the reporting ofdata of a data device associated with a vehicle. For this embodiment,both the real time data reporting and the periodic data reporting areenabled, but the scheduled reporting is not enabled. Specifically, theperiodic reporting is specified to report once every 15 minutes,beginning and 12:00 (noon). Further, the reporting packet includes amessage size of 16 bytes, wherein the preamble codes and the MCS arespecified. The data profile 420 includes a specific data processingfunction. The exemplary function includes determining whether the datadevice (and therefore, the vehicle associated with the data device) iswithin a geographical fence. While the data device is within thegeographical fence, the data device follows the periodic reportingschedule as specified by the data profile. If the data device isdetected to leave an area specified by the geographical fence, the realtime reporting flag is triggered, and the hub of the data deviceperformed real time communication with the base station that includes,for example, the location of the data device as detected outside of thegeographical fence.

FIG. 5 shows results of data smoothing due to data source profileadjustment, according to an embodiment. As shown in FIG. 5, the dataprofile can be used to smooth the communication of data of a data sourcefrom a hub of the data source to a base station. As shown, beforeselecting and/or adjusting the data profile, the channel resourcerequest of a particular data device may exceed the resources available(service limit) through the wireless satellite link. However, afterselecting and/or adjusting the data profile, the timing of thecommunication can be selected to smooth the data reporting which doesnot exceed the service limit of the wireless satellite link.

For at least some embodiments, data traffic of reporting data devices issmoothed to yield channel resource requests to below a service limitthreshold (shown as the service limit in FIG. 5) by adjusting a phaseoffset with the data profile of periodic reporting of data of one ormore data devices. As previously stated, the adjusting the phase offsetincludes adjusting a relative timing of the reporting of periodic data.For an embodiment, the phase offsets of the data profiles of differentdata devices are spread over wider widows of time. Inferiorimplementations may select convenient times, such as, on the hour, or onthe half hour. However, the described embodiments include adjustments ofthe phase offset of different devices which provides for the smoothingof the data traffic.

For at least some embodiments, data traffic of reporting data devices issmoothed by adjusting for certain applications the periodicity of thedata reporting of different data devices. For an embodiment, thisincludes adjusting the periodicity to reflect current networkconditions. As an example, applications of data devices under certainSLAs (service level agreements) may have their periodicity reducedduring peak usage hours which may be found, for example, during harvestseason, holidays, or other time periods where human/machine interactionsincrease. Peak usage hours can be identified a priori or can beidentified by monitoring traffic conditions over time, and identifyinghigh (greater than a threshold) periods of data traffic.

FIG. 6 shows control channel efficiencies and the effects assignments ofpreamble codes can have on the control channel efficiencies, accordingto an embodiment. Before intelligent assignment of preamble codes, theefficiency of a control channel may have the characteristics of curve610. That is, the efficiency of the control channel may increase as thenumber of devices increases. However, at some point, as the number ofdevices increases, the efficiency levels off, and then greatly decreaseswith increases in the number of devices.

However, by intelligently selecting preambles for packets of reportingdata, the efficiency of the control channel can be improved greatly asshown by curve 620. For example, reporting times of different datadevices of different hubs can be monitored over time. Based on themonitoring, preamble codes for different devices can be selected suchthat devices that typically report at common times have orthogonalcodes. The assignment of orthogonal codes reduces the possibility of thepackets of these devices from interfering with each other. Further, thetiming of the reporting can be adjusted through the data profiles.

For at least some embodiments, the network management element curatesmeta-data about the data devices and data sources connected to thenetwork through the base stations. For an embodiment, this meta-dataincludes RACH probability density functions. For an embodiment, theseprobability density functions are used to optimally assign preamblecodes between devices to minimize the infinity norm of the expectedvalue (highest value) of RACH requests of the same preamble code. TheRACH probability density functions can be determined by monitoring theactivity during specified RACH periods of operation.

FIG. 7 shows a dynamic allocation of control channel versus datachannel, according to an embodiment. A first control channel allocation710 occupying a first amount of frequency and time resources of thewireless link.

The resources allocated to the control channel can be reduced withutilization of intelligent preamble assignments within the data sourceprofiles. A second control channel allocation 720 occupying a secondamount of frequency and time resources of the wireless link which isless than the first control channel allocation 710.

Without “intelligent” preamble code allocations, maximum efficiency ofcontrol channel is 1/e, resulting in excess radio resources(time/frequency) being allocated to RACH (random access channel) whichcould have otherwise been allocated to data. The size of the RACHcontrol window can also have its requirements reduced through the use ofthe fine control adjustments to the roundtrip timing when using thelocation-based embodiment shown in FIG. 2.

FIG. 8 is a flow chart that includes steps of a method of coordinatingaccess of a plurality of devices across a satellite link, according toan embodiment. A first step 810 includes providing, by each of aplurality of hubs, a unique identifier to a network management elementassociated with a base station, wherein the providing includeswirelessly transmitting, by each of the hubs, the unique identifier tothe base station through a wireless satellite link. A second step 820includes receiving through the wireless satellite link, by each hub, oneor more data profiles back from the network management element whereineach of the one or more data profiles correspond with one or more datasources associated with the hub. A third step 830 includes receiving, byeach hub, data from the one or more data sources associated with thehub. A fourth step 840 includes controlling, by each hub, a timing ofcommunication of the data for each of the one or more data sources fromthe hub to the base station through the wireless satellite link based onthe data profile corresponding with the data source, wherein the dataprofile of each of the data sources of each of the hubs maintainsynchronous timing of the communication of the data of each of the datasources of each of the hubs with respect to each other. For at leastsome embodiments, the network management element further allocates perthe data profiles a frequency for the communication between each of thehubs and the base station, for each of the data sources of each of thehubs.

As described, for at least some embodiments, the data profiles controlthe timing of the reporting of the data of the different data sources tosynchronize the data reporting and control (dictate) the radio resource(such as, time and frequency) between the hubs and the base station. Forat least some embodiments, the data profile for each data sourceincludes a rule set for the data source, wherein the rule set controlsthe timing of communication. The rule set of the data profile incontrast to, for example, to a MAC (medium access control) schedule isset and used by the hubs for controlling the communication until thedata profile is updated due to a triggering event.

For an embodiment, the network management element communicates a profileadaptor to one or more of the hubs. For an embodiment, this includes thenetwork management element broadcasting rule sets used by hub tocontrol/process the data profile(s). For an embodiment, when a hubreceives the profile adaptor, if QOS of the data profile is less than xthen the hub changes, for example, the periodicity of periodictransmissions of a data source for a threshold period of time or untilanother message (such as, another profile adaptor) with a new rule setis received.

For an embodiment, the rule set includes device dependencies of the dataprofile. For example, the rule set may include time and location statesof the data device dependency of the data profile.

For an embodiment, the hub collects the data of the data devices, butdoes not transmit the data until the network management element solicitsthe hub for data transmission. For an embodiment, the hub informs thenetwork management element of restrictions and/or requirements of thehub or the data device associated with the hub. For example, the hub maybe specified by the data profile to transmit once a day, but the hub isavailable to transmit only at a particular time of the day (for example,6 pm to 6 am). The hub may inform the network management element aboutits restrictions/requirements.

For at least some embodiments, the data profile is used to parse (filteror selectively remove or eliminate) raw data from connected datasources. Most commercially available sensors are designed forterrestrial networks and are often overly verbose (include a largeamount of excess data) when transmitting data. A core function of theutilization of the data profile is to understand and map the data schemaof a sensor to extract “filter” only the relevant and most importantinformation. For example, a data report that includes “Engine RPM: 3000”may be filtered by the data profile of the data device down to “3000”which is then interpreted in the context of the data profile. That is,for an embodiment, based upon prior information “standard reporting ofthe specific device” of the specific data devices the data profile isselected to only transmit the selected datums which are a subset of thestandard reporting. This filtering of the reported data intelligentlyreduces the amount of data reported which reduces the demand on theresource (for example, the wireless link) used by each data device.

As previously stated, the described embodiments of the data profilesallow for the elimination of redundant data channel setup informationwhich is already contained inside the data profile, and is no longerneeded to be shared upon the initiation of every packet sent across thenetwork. This information may include the transmission size, sub-carrier(frequency) allocation, MCS selection, and timing information. Theresult of this is a reduction in data resources consumed by the networkto send a packet of data.

Further, as shown for example by the data profile 420 of FIG. 4, thedata profile includes the ruleset for radio resource allocation. As anexample, the ruleset for selecting transmission timing may includeintegrating forward in time a periodic phase offset the integratedperiodicity of periodic reporting. For an embodiment, the ruleset mayinclude user defined functions and routing (for example, geo-fencing ortemperature reporting).

As described, at least some embodiments include the data profile of eachdata device being used to dictate or change radio resource allocationsand general modem operating procedures supported on an applicationlevel. For an embodiment, the data profile of a data device is used tochange, update, or modify link-layer or application layer encryptionschemes as a function of a location of the data device, and/or the timeof day. It may be desirable, for a data device to maintain a higherlevel of security of reported data based on the location of the datadevice, and/or the time of reporting of the data of the data device.

For an embodiment, the data profile of a data device is used to change,update, or modify muting or attenuation of a transmission signal powerof the reported data as a function location of the data device, the timeof day, and/or network loading. For at least some embodiments, rulesetsof the data profile are used for directing how and when to do channelestimation of the communication channel of the wireless link between thehub of the data device and the base station. For an embodiment, the dataprofile of the data device controls the timing of the channel estimationbased on the application of the data device. For example, a mobile fleetmanagement application may be directed by the device profile to dochannel estimation more often (and/or as a function of velocity) anddifferently than a stationary agriculture sensor. That is, the channelof a mobile device will change more frequently than a stationary device,and the data profile of the mobile device will direct the communicationchannel of the mobile data device to be remeasured more frequently. Foran embodiment, the rulesets of the data profiles control powermanagement of the hub via satellite transmissions of the hub. As anexample, a user case such as fishing where users charge their deviceevery night may utilize higher MCS, less repetitions, more output powerto achieve the most efficient and reliable link possible. Otherapplications such as long-distance trucking may utilize less spectrallyefficient methods to transmit their data, but methods which are moreenergy efficient.

As shown in FIG. 2, at least some embodiments include adjusting the dataprofile for each data source based at least in part on a location of thedevice, wherein the data profile adjustment mitigates differences inpropagation time of communication propagating from each hub to the basestation. Further, as described, other methods include determining thedifferences in propagation times based on measured propagation delays.For at least some embodiments, the data profiles for the data deviceinclude a function to calculate a timing advance based upon the location(for example, GPS location) of the data device, and a static location ofthe satellite the hub of the data device is wirelessly linked to thebase station through. For an embodiment, this function of the dataprofile is updated whenever the device transits to a differentsatellite.

For at least some embodiment, a data profile supports multiple datadevices. That is, for example, the network management element determinesa data profile for multiple data devices. For an embodiment, the dataprofile supports multiple data devices with overlapping transmissioncharacteristics. Through management of the data profile, utilization ofthe wireless link between the hub and the base station can be moreefficiently used. That is, transmission overhead, such as, random accesstransmission, and control message overhead, can be more efficient due tothe management of the data profile for multiple data device. If forexample, two different data devices have data to be transmitted within athreshold duration of time, a single data profile can be managed for thedata devices. The data of the data devices can be merged. For anembodiment, the merging of the data means the data of the different datadevices are transmitted from the hub to the base station using a singledata blob (for example, a data packet) using a single grant message fromthe network management element. For an embodiment, the hub adds aproprietary wrapper/header to define data boundaries and associate datato different devices. For example, wrapper can include a data startindex and a size for each data device.

For at least some embodiments, controlling the timing of thecommunication of the data for each of the one or more data sources fromthe hub to the base station through the wireless link includes selectingthe timing as one of real-time communication, scheduled communication,or periodic communication based on the data profile selected for thedata source. For at least some embodiments, different data sources ofthe hub have different data profiles that include differently controlledtiming of communication of data of the different data sources of fromthe hub to the base station. For at least some embodiments, a dataprofile of at least one data source of the hub controls timing ofcommunication of data of at least one data source according to more thanone type of controlled timing based on characteristics of the data ofthe at least one data source.

Real-time, periodic, and scheduled transmissions are unique transmissiontypes on the link layer. However, different data movement manifestationscan occur in the context of the application layer. For an embodiment, anapplication layer transmission mode includes a store and forward mode.For an embodiment, the store and forward mode includes locally storingin memory one or many device datums to aggregate prior to sending thedata over the network using one of the link layer mechanisms. Thecombination of data processing and/or routing and the selection of alink layer transmission mechanism creates an application layertransmission mechanism. For example, data from a sensor of a data devicecan be collected in a local buffer of the data device until the bufferreaches X capacity and then the data device (as dictated by the dataprofile of the data device) transmits that data immediately. This is anexample of an application layer “store and forward” mechanism that isbuilt with a real time link layer transmission combined with datastorage and processing functions from the data profiles.

For an embodiment, an application layer transmission mode as defined bythe data profile of a data device includes a data pull mode. For anembodiment, the data pull mode cumulatively storing live datum untilrequested by a user. For example, through the data profile, a datadevice may be directed to store the latest temperature reading andtransmit that reading over the network when requested by a user via aweb console through a top down route via the base station and networkmanagement element.

At least some embodiments further include updating, by the networkmanagement element, the profile of one or more of the data sources. Atleast some embodiments further include adaptively updating the profileby a network operation center based on data communication activity of atleast the base station. For at least some embodiments, the datacommunication activity includes network traffic congestion. For at leastsome embodiments, the data communication activity includes wirelesscommunication between the hubs and the base station, and communicationbetween the data sources and the hubs. For at least some embodiments,the data communication activity includes a composition of data trafficbetween real-time traffic, scheduled traffic, and periodic traffic. Forat least some embodiments, the data profile is updated based on at leastone of a data load of the network, a user selection, customeracquisition, or application.

For at least some embodiments, the hub autonomously updates a dataprofile of a data device based on a sensed orientation of the hub of thedata device. For an embodiment, the hub pushes the data profile updateto the network management element. For example, when the orientation ofthe hub is placed upside down, this sensed orientation of the hub can besensed, and the data profiled of a data device connected to the hub canbe adaptively updated to operate in a store and forward mode. For anembodiment, orientation of the hub is sensed and the data profile isupdated based on the sensed orientation to affect radio transmissionparameters of the wireless communication between the hub and the basestation. For example, the orientation of the hub can be detected using a9-axis IMU (accelerometer, gyroscope, magnetic sensor, all sensing 3orientations). Based on the sensed orientation of the hub, the dataprofile of the data device connected to the hub is adaptively updated todictate, for example, the MCS, repetition, and/or other radio parametersto adjust for loss of gain from antenna or other link budget factorsthat are effected by the orientation of the hub.

For at least some embodiments, the data profile sets a packet size ofcommunication of data of a data source that is communicated through thewireless link. For an embodiment, the packet size is selected to helpreduce overhead—and save the shared resource (wireless link). Further,for an embodiment, the selected data profile includes a selected MCS(modulation and coding scheme) based on the data source and theapplication being served.

For an embodiment, the packet size and/or list of datums that aretransmitted over the network is updated based upon an “active/notactive” flag. For an embodiment, setting the flag may come fromdirecting sensing on the hub (for example, an IMU, GPS, temperature) ormay come into the data profile directly from the sensor as a flag. Bothsides of the wireless link (hub and base station) need to a priori knowthe packet size in order to support the wireless communication betweenthe hub and the base station.

For at least some embodiments, the data profiles include preamble codes,and wherein for real-time communication, the preamble codes are insertedinto packets of the data sources to uniquely identify the data source ofthe packet during real-time communication. At least some embodimentsfurther include the network management element selecting the preamblecode for the data source based on a historical analysis of real-timetransmission timings of the hub of the data source and other datasources. For an embodiment, different preamble codes are allocated todata sources that historically report within a margin of time, andsimilar codes are allocated to data sources that historically report atdisparate times. For an embodiment, different preamble codes areassigned to data devices base on a QoS (quality of service) to minimizecongestion of data traffic been the base station and the hubs.

At least some embodiments further include processing, by one of more ofthe hubs, the data of the data source, and communicating the processeddata through the wireless link to the base station. For an embodiment,the processing includes filtering the data. An embodiment includes onlycommunicating (reporting) a type of data if a threshold condition issatisfied. For an embodiment, the processing includes synthesizing dataof more than one data source. For an embodiment, synthesizing includescombining the data of more than one data source before reporting. For anembodiment, synthesizing includes filtering data of one source based onvalues of data of a second data source.

FIG. 9 shows a plurality of hubs 910, 990 that communicate data of datasources 911, 912, 913, 914, 915 through a shared resource to a basestation, according to an embodiment. As shown, the data sources 911,912, 913, 914, 915 are connected to the hubs 910, 990. The hubs 910, 990communicate through modems 930, 932 to a modem 945 of the base station940 through the wireless links. For an embodiment, the wireless linksare a shared resource 999 that has a limited capacity. The describedembodiments include data profiles which are utilized to provideefficient use of the shared resource 999. The base station may alsocommunicate with outside networks 970, 980.

As previously described, it is to be understood that the data sources911, 912, 913, 914, 915 can vary in type, and can each require verydifferent data reporting characteristics. The shared resource 999 is alimited resource, and the use of this limited resource should bejudicious and efficient. In order to efficiently utilize the sharedresource 999, each of the data sources 911, 912, 913, 914, 915 areprovided with data profiles 921, 922, 923, 924, 925 that coordinate thetiming (and/or frequency) of reporting (communication by the hubs 910,990 to the base station 940 through the shared resource 999) of the dataprovided by the data sources 911, 912, 913, 914, 915.

For an embodiment, a network management element 950 maintains a database960 in which the data profiles 921, 922, 923, 924, 925 can be stored andmaintained. Further, the network management element 950 manages the dataprofiles 921, 922, 923, 924, 925, wherein the management includesensuring that synchronization is maintained during the data reporting bythe hubs 910, 990 of the data of each of the data sources 911, 912, 913,914, 915. That is, the data reported by each hub 910, 990 of the data ofthe data sources 911, 912, 913, 914, 915 maintains synchronization ofthe data reporting of each of the data sources 911, 912, 913, 914, 915relative to each other. Again, the network management element 950ensures this synchronization through management of the data profiles921, 922, 923, 924, 925. The synchronization between the data sources911, 912, 913, 914, 915 distributes the timing of the reporting of thedata of each of the data sources 911, 912, 913, 914, 915 to prevent thereporting of one device from interfering with the reporting of anotherdevice, and provides for efficiency in the data reporting.

For at least some embodiments, the network management element 950resides in a central network location perhaps collocated with multiplebase stations and/or co-located with a network operations center (asshown, for example, in FIG. 3). For an embodiment, the networkmanagement element 950 directly communicates with the base station 940and initiates the transfer of data profiles across the network via thebase station 940 to the hubs 910, 990.

For at least some embodiments, data profiles are distributed when newhubs are brought onto the network, when hubs change ownership, or whenthe hubs are re-provisioned. Other changes to data profile contentsoutside of these situations are more likely addressed by sync packets(for an embodiment, a sync packet is a packet to update the value of aspecific field inside of a data profile, but not necessarily updatingthe structure of the data profile) were only small changes to profilefields are required.

As described, the data profiles 921, 922, 923, 924, 925 control timingof when the hubs 910, 990 communicate the data of the data sources 911,912, 913, 914, 915 through the shared resource 999. Accordingly, thedescribed embodiments coordinate access to the shared resource 999 toinsure optimal usage of the network resource to avoid collisions betweenpackets, the transmission of redundant information, and to reshapeundesired traffic profiles.

Although specific embodiments have been described and illustrated, theembodiments are not to be limited to the specific forms or arrangementsof parts so described and illustrated. The described embodiments are toonly be limited by the claims.

What is claimed:
 1. A method of coordinating access of a plurality ofdevices across a wireless link, comprising: receiving through thewireless link, by each hub of a plurality of hubs associated with a basestation, one or more data profiles from a network management element;receiving, by each hub, data from one or more data sources associatedwith the hub; controlling, by each hub, a timing of communication of thedata for each of the one or more data sources from the hub to the basestation through the wireless satellite link based on the one or moredata profiles; monitoring reporting times of different data sources ofdifferent hubs over time; allocating preamble codes to each of the datasources, wherein different preamble codes are allocated to differentdata sources of different hubs that report within a margin of time ofeach other; and inserting the allocated preamble codes into packets ofeach of the data sources; wherein the one or more data profiles of eachof the hubs maintain synchronous timing of the communication of the dataof each of the hubs with respect to each other.
 2. The method of claim1, further comprising adjusting a data profile for each data sourcebased at least in part on a location of the data source, wherein thedata profile adjustment mitigates differences in propagation time ofcommunication propagating from each hub to the base station.
 3. Themethod of claim 2, wherein the data profile adjustment includes atransmission delay that includes a course delay and a fine delay,wherein a single course delay is associated with each base station, anda different fine delay is associate with each hub of each base station,wherein the fine delay is determined for each hub based on the locationof the hub.
 4. The method of claim 1, wherein controlling the timing ofthe communication of the data for each of the one or more data sourcesfrom each hub to the base station through the wireless link comprisesselecting the timing as one of real-time communication, scheduledcommunication, or periodic communication based on a data profileselected for the data source.
 5. The method of claim 4, whereindifferent data sources of the hub have different data profiles thatinclude differently controlled timing of communication of data of thedifferent data sources from the hub to the base station.
 6. The methodof claim 4, wherein a data profile of at least one data source of thehub controls timing of communication of data of at least one data sourceaccording to more than one type of controlled timing based oncharacteristics of the data of the at least one data source.
 7. Themethod of claim 1, further comprising updating, by the networkmanagement element, a data profile of one or more of the data sources.8. The method of claim 7, further comprising adaptively updating thedata profile by a network operation center based on data communicationactivity of at least the base station.
 9. The method of claim 8, whereinthe data communication activity includes network traffic congestion. 10.The method of claim 8, wherein the data communication activity includeswireless communication between the hubs and the base station, andcommunication between the data sources and the hubs.
 11. The method ofclaim 8, wherein the data communication activity includes a compositionof data traffic between real-time traffic, scheduled traffic, andperiodic traffic.
 12. The method of claim 8, wherein the data profile isupdated based on at least one of a data load of the network, a userselection, customer acquisition, or application.
 13. The method of claim1, wherein the one or more data profiles set a packet size ofcommunication of data of a data source that is communicated through thewireless link.
 14. The method of claim 1, wherein the one or more dataprofiles include the allocated preamble codes, and wherein for real-timecommunication, inserting the allocated preamble codes into packets ofthe data sources uniquely identifies the data source of the packetduring real-time communication.
 15. The method of claim 15, furthercomprising the network management element selecting the allocatedpreamble code for the data source based on a historical analysis ofreal-time response times of the data source and other data sources. 16.The method of claim 1, further comprising processing, by one or more ofthe hubs, the data of the data source, and communicating the processeddata through the wireless link to the base station.
 17. The method ofclaim 16, wherein the processing includes filtering the data.
 18. Themethod of claim 17, wherein the processing includes synthesizing data ofmore than one data source, wherein synthesizing includes combining thedata of more than one data source before reporting.
 19. A system forcoordinating access of a plurality of devices across a wireless link,comprising: at least one base station, the at least one base stationoperative to communicate with each of a plurality of hubs through thewireless link; each of the plurality of hubs connected to one or moredata sources, and operative to: receive through the wireless link one ormore data profiles back from a network management element; receive datafrom the one or more data sources associated with the hub; control atiming of communication of the data for each of the one or more datasources from the hub to the base station through the wireless satellitelink based on the data profile; wherein reporting times of differentdata sources of different hubs are monitored over time; wherein preamblecodes are allocated to each of the data sources, wherein differentpreamble codes are allocated to different data sources that reportwithin a margin of time of each other; wherein each hub further operatesto insert the allocated preamble codes into packets of each of the datasources; wherein the data profile of each of the hubs maintainsynchronous timing of the communication of the data of each of the hubswith respect to each other.
 20. A hub for coordinating access of aplurality of devices across a wireless link, comprising: a modemoperative to communicate with a modem of a base station through thewireless link; a controller operative to: receive through the wirelesslink one or more data profiles from a network management element;receive data from the one or more data sources associated with the hub;control a timing of communication of the data for each of the one ormore data sources from the hub to the base station through the wirelesssatellite link based on the data profile corresponding with the datasource; monitor reporting times of different data sources of differenthubs over time; allocate preamble codes to each of the data sources,wherein different preamble codes are allocated to different data sourcesthat report within a margin of time of each other; wherein each huboperates to insert the allocated preamble codes into packets of each ofthe data sources; wherein the data profile of each of the hubs maintainsynchronous timing of the communication of the data of each of the hubswith respect to each other.